-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Renovate's pip_requirements
Manager
#764
Conversation
🚲 PR staged at http://34.133.220.217 |
Do you mean "instead of updating the requirements.txt file first"? LGTM! |
🚲 PR staged at http://34.133.220.217 |
Good question. Christine and I just did some digging and decided to keep Background Info
|
pip_requirements
pip_requirements
pip_requirements
Manager
Looks like this is not behaving as expected, for example in the PRs opened this morning
The |
I think we should try this renovatebot/renovate#10407 (comment)
|
Oh no. This is a fun game of whack-a-mole. 😄 Thanks for sharing those links and bringing this to our attention, Christine.
I see. Let's try your suggestion of adding:
🤞 |
* Disable Renovate for Python, temporarily * Disable pip_requirements & enable pip-compile
Follows the advice of [here](GoogleCloudPlatform/microservices-demo#764) to disable pip_requirements and explicitly mark pip-compile to do lockFileMaintenance (which I think was on by default, but ...)
ty folks for these good writeups! I faced the same thing this week and randomly found this very helpful conversation :) |
Background
requirements.txt
file, instead of updating therequirements.txt
file first.requirements.in
file.Fixes
N/A
Change Summary
Additional Notes
requirement.txt
bumps, and hope nothing goes wrong. I might be overthinking this.Testing Procedure
Related PRs or Issues
N/A